Skip to content

Fix provided scope warnings for Maven plugin dependencies#526

Open
xjusko wants to merge 1 commit intoshrinkwrap:masterfrom
xjusko:fix-provided-scope-warnings
Open

Fix provided scope warnings for Maven plugin dependencies#526
xjusko wants to merge 1 commit intoshrinkwrap:masterfrom
xjusko:fix-provided-scope-warnings

Conversation

@xjusko
Copy link
Copy Markdown
Contributor

@xjusko xjusko commented Apr 22, 2026

Set Maven API dependencies to provided scope in the maven-plugin module, as they are supplied by the Maven runtime when executing the plugin.

fixes #520

Set Maven API dependencies to provided scope in the maven-plugin module,
as they are supplied by the Maven runtime when executing the plugin.
@xjusko
Copy link
Copy Markdown
Contributor Author

xjusko commented Apr 23, 2026

I am not 100% sure we want to go through with this change. It creates clutter in the code; however, in the past, we encountered some issues with dependencies where the provided scope was missing.

@petrberan
Copy link
Copy Markdown
Member

Do we use all of those dependencies?

@xjusko
Copy link
Copy Markdown
Contributor Author

xjusko commented Apr 23, 2026

@petrberan The plugin code uses maven-plugin-api, maven-core, and maven-model directly via imports. The remaining 7 are transitive from shrinkwrap modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Some dependencies of Maven Plugins are expected to be in provided scope.

2 participants